Realized a while back that IG on web finally has support to save posts "into collections". And that also indicates why the add to collection tap action is slow as a snail that I tweeted about last week. For each collection, end point returns pretty much all you can ask for about it.
I have about 12 collections between memes and interior design posts. So, multiply this response object by that. Firefox marks it a slow response in dev tools; of course.
Each of these with duplicated fields, every asset size URL for each.
In reality all that is of need would be three keys per object.
- the collection name
- cover image (presume IG chooses the first image added as cover, until changed).
- some metadata for client
The irony of this entire situation is, talks of GraphQL don't seem to have translated. Over querying by application design is not solved, I presume, by any supposed panacea.